Multi-function devices to populate parameters for configuration files via communication with networked multi-function devices

ABSTRACT

A multi-function device (MFD) is disclosed. For example, the MFD includes a communication interface to establish a communication path with a network, a user interface to display a plurality of fields associated with different settings of a configuration file of the MFD, a processor, and a non-transitory computer-readable medium storing a plurality of instructions. The instructions when executed by the processor cause the processor to detect selection of a field associated with a setting of the configuration file, establish a connection with at least one networked MFD on the network, query the at least one networked MFD for a value used in the field associated with the setting of the configuration file that is selected, receive the value from the at least one networked MFD, and populate the field with the value.

The present disclosure relates generally to multi-function devices andrelates more particularly to a method and apparatus to populateparameters for configuration files via communication with networkedmulti-function devices.

BACKGROUND

Multi-function devices (MFDs) are devices that can perform a variety ofdifferent functions. The MFDs can print, scan, copy, fax, emaildocuments, and the like. The MFDs can provide a variety of differentoptions to perform the various job requests, such as different colors,different paper sizes, changing a print quality, changing a size of theimage and/or text to be printed, stapling, collating, providingdifferent email addresses, selecting which network storage service tosend the scanned document to, and the like.

Thus, MFDs are complex devices that may involve many differentconfiguration settings to operate properly. The configuration settingsmay determine how the MFD communicates over a particular communicationnetwork, how the MFD communicates with other endpoint devices, how thesoftware presents a graphical user interface, and the like.

SUMMARY

According to aspects illustrated herein, there are provided amulti-function device (MFD) and a method for automatically populatingparameters for configuration files via communication with networkedMFDs. One disclosed feature of the embodiments is an MFD that comprisesa communication interface to establish a communication path with anetwork, a user interface to display a plurality of fields associatedwith different settings of a configuration file of the MFD, a processor,and a non-transitory computer-readable medium storing a plurality ofinstructions. The instructions when executed by the processor cause theprocessor to detect selection of a field associated with a setting ofthe configuration file, establish a connection with at least onenetworked MFD on the network, query the at least one networked MFD for avalue used in the field associated with the setting of the configurationfile that is selected, receive the value from the at least one networkedMFD, and populate the field with the value.

Another disclosed feature is a method for automatically populatingparameters for configuration files via communication with networkedMFDs. The method executed by a processor of the MFD comprises detectinga selection of a field associated with a setting of a configurationfile, establishing a connection with at least one networked MFD on anetwork, querying the at least one networked MFD for a value used in thefield associated with the setting of the configuration file that isselected, receiving the value from the at least one networked MFD, andpopulating the field with the value.

BRIEF DESCRIPTION OF THE DRAWINGS

The teaching of the present disclosure can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates a block diagram of an example network that includes amulti-function device (MFD) to set parameters for configuration filesvia communication with networked MFDs of the present disclosure;

FIG. 2 illustrates a block diagram of an example MFD of the presentdisclosure;

FIG. 3 illustrates an example screen shot of a graphical user interfacethat shows settings for a configuration file that is automaticallypopulated with a value by the MFD via communication with networked MFDs;

FIG. 4 illustrates another example screen shot of a graphical userinterface that shows settings for a configuration file that isautomatically populated with a value by the MFD via communication withnetworked MFDs;

FIG. 5 illustrates a flow chart for a method of automatically populatingparameters for configuration files via communication with networked MFDsof the present disclosure; and

FIG. 6 illustrates a high-level block diagram of an example computersuitable for use in performing the functions described herein.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures.

DETAILED DESCRIPTION

The present disclosure broadly discloses a method and apparatus forautomatically populating parameters for configuration files viacommunication with networked multi-function devices (MFDs). As discussedabove, MFDs are complex devices that may involve many differentconfiguration settings to operate properly. The configuration settingsmay determine how the MFD communicates over a particular communicationnetwork, how the MFD communicates with other endpoint devices, how thesoftware presents a graphical user interface, and the like.

An experienced technician may be able to easily configure all of thesettings of the MFD. However, some companies may have large amounts ofturnover and use inexperienced technicians that may not be familiar withall of the values for each setting of the configuration files of theMFD. As a result, configuring the MFD to be ready to operate and/orcommunicate within the network may be slow and inefficient.

The present disclosure provides an apparatus and method that allows theMFD to communicate with other networked MFDs to obtain values fordifferent settings or parameters of a configuration file. For example,when a technician has opened a configuration file, the configurationfile may have a plurality of different fields to enter values for thedifferent settings. When a user clicks on a field, the MFD maycommunicate with other networked MFDs to obtain used values for theselected setting. The MFD may then populate the field with the mostpopular value that is used for the selected setting based on polling theother networked MFDs.

In one embodiment, the MFD may present a list of possible values to thetechnician on a user interface. For example, the list may be presentedas a pop-up window on the user interface. The list of values may beorganized from most used value to least used value.

In one embodiment, the MFD may present values from MFDs that have asimilar model number. For example, different model MFDs may usedifferent settings. Thus, the values presented to the technician may notbe the most popular or most used values, but may be values received froma networked MFD that has a same or similar model number.

In one embodiment, the MFD may have a timer that expires beforepresenting the values obtained from the other networked MFDs. Forexample, the technician may find it annoying if a pop-up window appearsafter selecting each field in the configuration file. The technician mayknow the values to enter for most of the fields. However, if thetechnician is not sure, the technician may hover or select a field andnot provide any input until the timer expires. In response, the MFD maypresent a list of values, assuming that the technician does not knowwhat value to use if no input is provided before expiration of thetimer.

Thus, the present disclosure may automatically provide values andpopulate settings of a configuration file. This may help expediteconfiguration of MFDs in the field when they are initialized or resetfor technicians, and especially for inexperienced technicians. Thus,configuration of the MFDs may be made more efficient.

FIG. 1 illustrates an example network 100 of the present disclosure. Inone embodiment, the network 100 may include an Internet protocol (IP)network 102. The IP network 102 may include a plurality of networkedmulti-function devices (MFDs) 104, 106, 108, and 110. Although four MFDsare illustrated in FIG. 1 , it should be noted that any number of MFDsmay be deployed in the IP network 102.

In one embodiment, the MFDs 104, 106, 108, and 110 may be networkedtogether on a common network. For example, the IP network 102 may be aparticular Wi-Fi network, and the MFDs 104, 106, 108, and 110 may beconnected to the same Wi-Fi network. In another embodiment, the MFDs104, 106, 108, and 110 may be connected via a wired (e.g., an Ethernetconnect) or a wireless connection to an enterprise local area network(LAN). In another example, the MFDs 104, 106, 108, and 110 may be partof a company network that spans different geographic locations but ispart of a private network of the enterprise. In other words, the MFDs104, 106, 108, and 110 may be grouped together such that each MFD 104,106, 108, and 110 can communicate with the others over the IP network102.

In one embodiment, each of the MFDs 104, 106, 108, and 110 may be adevice that can perform a variety of different job functions. Forexample, each MFD 104, 106, 108, or 110 may be able to perform print,copy, fax, scan, and email document functions.

In one embodiment, the IP network 102 may be any type of communicationnetwork that can transfer data using internet protocols. The IP network102 may be the Internet, for example. The IP network 102 has beensimplified for ease of explanation and may include additional networkelements that are not shown. For example, the IP network 102 may includefirewalls, gateways, switches, border elements, access networks, and thelike.

In one embodiment, the MFD 104 may include a display 112 that canpresent a user interface. The MFD 104 may include a configuration file114 and a configuration file settings value database 116 (also referredto herein as database 116). As noted above, a technician may be deployedto populate values for settings in the configuration file 114. However,the technician may not know what values to enter in the fields for someof the settings.

In one embodiment, the MFD 104 may communicate with the MFDs 106, 108,and 110 to request and receive values for various settings. The MFD 104may store those values in the database 116 to be presented to the useror technician, may present the values to the user via the user interfaceshown on the display 112 to allow the user to select one of the values,or may simply automatically populate the of the configuration file 114fields with values. As discussed in further detail below, the values maybe presented in an ordered list based on the values that are most usedby the MFDs 106, 108, and 110.

In another example, the values that are presented may be based on theMFDs 106, 108, and 110 that have a similar model number as a modelnumber of the MFD 104. For example, the MFD 106 may have the same modelnumber as the MFD 104. Thus, the value used for a setting in theconfiguration file 114 for the MFD 106 may be used by the MFD 104. Thevalue may be used even though it is not the most frequently used value.For example, the MFDs 108 and 110 may have different model numbers, butuse a different value (e.g., the different value used two times versusused only once for the value used by the MFD 106) than the value used bythe MFD 106.

In another embodiment, the values may be received in advance and storedin the database 116. The values from the database 116 for the varioussettings of the configuration file 114 may then be presented to theuser. The MFD 104 may periodically communicate with the MFDs 106, 108,and 110 to update the values in the database 116.

FIG. 2 illustrates a block diagram of an example of the MFD 104.However, the MFDs 106, 108, and 110 may be similar to the MFD 104 andmay include similar components. In one embodiment, the MFD 104 mayinclude a processor 202, a memory 204, a communications interface 208, auser interface 210, and a timer 212. The processor 202 may becommunicatively coupled to the memory 204, the communications interface208, the user interface 210, and the timer 212. The processor 202 maycontrol operation of and/or transmit/receive data via the communicationsinterface 208, and/or the user interface 210.

In one embodiment, the communications interface 208 may be to establisha communication path between the MFD 104 and the other MFDs 106, 108,and 110 via the IP network 102. For example, the communicationsinterface 208 may be a wireless or wired communication interface. Forexample, the communications interface 208 may be a WiFi radio, anEthernet connection, a fax over IP connection that uses an RJ-111connection, a cellular radio, and the like.

In one embodiment, the user interface 210 may be a graphical userinterface (GUI). The user interface 210 may be a touch screen interfaceor may be a GUI that receives inputs via a keyboard, mouse, a trackpad,and the like. The user interface 210 may be used to present theconfiguration file 114 to the user or technician via the display 112.Examples of the GUI and how the configuration file 114 is presented areillustrated in FIGS. 3 and 4 and discussed in further detail below.

In one embodiment, the timer 212 may be used to countdown a pre-definedamount of time after a user selects a field for a setting in theconfiguration file 114. The timer 212 may be optional. The timer 212 maybe used such that pop-up windows or fields are not continuouslypopulated. The technician or user may know the values for most of thesettings in the configuration file 114. Thus, it may be distracting tohave the values automatically populated or to have the pop-up windowappear each time a field is selected. The timer 212 may provide sometime (e.g., 10 seconds, 20 seconds, 30 seconds, and the like) to allowthe technician to enter the known value for a setting. If the techniciandoes not know the value, the technician may simply wait for the timer toexpire without providing an input or value. Once the timer 212 expires,the MFD 104 may automatically populate the field with a value or presentpossible values to the technician for selection. The timer 212 may resetand restart each time the technician selects another field for anothersetting of the configuration file 114.

In one embodiment, the memory 204 may be any type of non-transitorycomputer readable medium. For example, the memory 204 may be a hard diskdrive, a solid state drive, a random access memory, a read only memory,and the like. The memory 204 may store instructions 206.

In one embodiment, the instructions 206 may be executed by the processor202 to perform the functions described herein to automatically populateparameters for configuration files via communication with networkedMFDs. The instructions 206 may cause the processor 202 to performoperations of the method 500 illustrated in FIG. 5 , and discussed infurther detail below. In one embodiment, the memory 204 may also storethe configuration file 114 and the configuration file settings valuedatabase 116.

FIG. 3 illustrates an example screen shot 300 of a graphical userinterface (GUI) 302 that shows settings for the configuration file 114that is automatically populated with a value by the MFD 104 viacommunication with networked MFDs 106, 108, and 110. In one embodiment,the configuration file 114 may be displayed in the GUI 302 presented bythe display 112 of the MFD 104.

The configuration file 114 may include a plurality of different settings304 ₁ to 304 _(n) (hereinafter also referred to individually as asetting 304 or collectively as settings 304). The settings 304 mayinclude different settings for the MFD 104 to function properly. Thesettings 304 may be associated with network settings, driver settings,operating system settings, hardware settings, and the like. For example,the settings 304 may include port numbers and/or assignments, internetprotocol (IP) addresses, domain name services (DNS) values, interfaceassignments, graphics settings, memory allocations, device configurationsettings, peripheral device settings, passwords, power managementvalues, and the like.

Each setting 304 may have a corresponding field 306 ₁ to 306 _(n)(hereinafter also referred to individually as a field 306 orcollectively as fields 306). A user may move a pointer 308 or simplytouch a field 306 (in the case of a touch screen GUI) to enter a valuefor the corresponding setting 304.

In one embodiment, when the user selects the field 306 ₃ to enter avalue for the setting 304 ₃, the MFD 104 may populate a value in thefield 306 ₃ or the MFD 104 may present a pop-up window 310 with values312 and 314. In one embodiment, the values 312 and 314 may be obtainedfrom the configuration file settings value database 116. The database116 may be generated by the MFD 104 by communicating with the other MFDs106, 108, and 110 to receive values associated with the settings 304.

In one embodiment, when the user selects the field 306 ₃, the MFD 104may establish a communication session with at least one of the MFDs 106,108, and 110 or with all of them. The MFD 104 may query the MFDs 106,108, and 110 for a value that is used for the setting 304 ₃. The MFDs106, 108, and 110 may transmit the values for the setting 304 ₃ used bythe MFDs 106, 108, and 110.

In one embodiment, the MFD 104 may order the values 312 and 314 in thepop-up window 310. In one embodiment, the values 312 and 314 may beordered from most used to least used. For example, the value 312 may beused by the greatest number of MFDs and the value 314 may be used by thefewest MFDs. For example, the value 312 may be used by the MFD 108 and110, and the value 314 may be used by the MFD 106.

In one embodiment, the MFD 104 may order the values 312 and 314 usingpriority based on MFDs that have a same model number as the MFD 104. Forexample, the MFD 108 may have a same model number as the MFD 104. Thus,the MFD 104 may likely want to be configured similar to the MFD 108.Thus, the value 312 used by the MFD 108 with the same model number maybe listed first, then the value 314 used by the other MFDs may be listedafter. Notably, the value 314 may be used by a greater number of MFDs,but still be listed below the value 312 in this example.

The user may select a desired value 312 or 314 from the pop-up window310. The MFD 104 may then populate the field 306 ₃ with the value 312 or314 that is selected by the user for the setting 304 ₃.

In one embodiment, the timer 212 may be used to begin a countdown timerof a pre-defined expiration time period. The timer 212 may be used suchthat the pop-up window 310 is not shown for each field 306 that isselected. For example, it could become distracting if the user knows thevalue to input for some of the fields 306, but is constantly interruptedby the pop-up window 310. Thus, the timer 212 may wait the pre-definedexpiration time period before presenting the pop-up window 312 with thevalues 312 and 314.

To illustrate, when the user selects a field 306, the timer 212 may bebegin. If the MFD 104 detects an input before the timer expires, the MFD304 may stop the pop-up window 310 from appearing. However, if the MFD104 does not detect an input before the timer 212 expires, the MFD 104may generate the pop-up window 310 with the values 312 and 314 using themethods described above.

In one embodiment, using the timer 212 may also allow the MFD 104 toobtain the values 312 and 314 from the other MFDs 106, 108, and 110.Thus, while the timer 212 is counting down, the MFD 104 may obtain thevalues 312 and 314 in the background and have those values 312 and 314ready for presentation as soon as the timer 212 expires. Thus, the usermay not experience any lag or wait times to see the values 312 and 314in the pop-up window 310.

In one embodiment, the user may enter a key or right click on the field306 and select help to immediately bring the pop-up window 310. Forexample, if the user does not know the proper value, the user may callthe pop-up window 310 rather than waiting for the timer 212 to expire.

In one embodiment, after the user enters a value in the field 306 ₃, theMFD 104 may check the value against the values for the setting 304 ₃stored in the database 116 or against the values received from the otherMFDs 106, 108, and 110. If the value entered by the user does not matchany of the values stored in the database 116 or received from the otherMFDs 106, 108, and 110, the MFD 104 may generate a notification topresent to the user. The notification may indicate to the user that theentered value may not be correct and present the pop-up window 310 toshow the values 312 and 314 used by the other MFDs 106, 108, and 110.The user may then double check the entered value against the values 312and 314 in the pop-up window 310 or select to continue with the enteredvalue.

FIG. 4 illustrates another example screen shot 400 of the GUI 302 thatshows settings for a configuration file 114 that is automaticallypopulated with a value by the MFD 104 via communication with networkedMFDs 106, 108, and 110. The screen shot 400 illustrates an embodiment,where a value 402 is automatically populated into the field 306 ₃. Forexample, when the user selects the field 306 ₃ with the pointer 308, thevalue 402 may be automatically populated. The user may then change thevalue 402 with a different value if the user wants to use a differentvalue for the field 306 ₃.

Thus, in the embodiment illustrated in FIG. 4 , the user may simplyclick on the fields 306 ₁-306 _(n) one-by-one to have each of the fields306 ₁-306 _(n) automatically populated. Thus, a user may input valuesfor all of the fields 306 ₁-306 _(n) with a single click rather thanhaving to enter multiple keystrokes for the values. This may allow theuser to complete the configuration file 114 much faster, if theautomatically entered values 402 are acceptable to the user.

Thus, the MFDs of the present disclosure may automatically providevalues for settings of configuration files of the MFDs and populatefields for the settings with the values. This may allow inexperiencedtechnicians to quickly set values for the configuration file if thetechnician comes across settings that they are not familiar with.

FIG. 5 illustrates a flow chart of an example method 500 forautomatically populating parameters for configuration files viacommunication with networked MFDs of the present disclosure. In oneembodiment, the method 500 may be performed by the apparatus 102 or byan apparatus such as the apparatus 600 illustrated in FIG. 6 anddiscussed below.

In one embodiment, the method 500 begins at block 502. At block 504, themethod 500 detects a selection of a field associated with a setting of aconfiguration file. For example, a user may open a configuration file,and the configuration file may be presented in a GUI of the MFD. Theuser may select a field to enter a value for the setting.

At block 506, the method 500 establishes a connection with at least onenetworked MFD on a network. In one embodiment, in response to detectingthe selection, the MFD may establish a communication session with othernetworked MFDs. In one embodiment, the MFD may establish a communicationsession with a plurality of networked MFDs. For example, the MFD may beconnected to a same local network or enterprise network across severaldifferent geographic locations as the other networked MFDs. Theconnection may be a wired or wireless connection.

At block 508, the method 500 queries the at least one networked MFD fora value used in the field associated with the setting of theconfiguration file that is selected. For example, the MFD may determinethe setting associated with the field selected by the user. The MFD maythen query the other networked MFDs for the value that is used for thesetting.

At block 510, the method 500 receives the value from the at least onenetworked MFD. The other networked MFDs may transmit the value to theMFD. In one embodiment, the values may be ordered by the MFD. Forexample, the values may be ordered from most used to least used. In oneembodiment, the values may be ordered based on values used by othernetworked MFDs with the same model number as the MFD.

In one embodiment, the values may be presented to the user or technicianin a pop-up window on the GUI. The user may select a value to enter inthe field associated with a setting of the configuration file.

At block 512, the method 500 populates the field with the value. Forexample, the value selected by the user from the pop-up window may beused to populate the field. In one embodiment, the field may beautomatically populated with a value received from the other networkedMFDs. For example, instead of presenting the values to the user via thepop-up window, the MFD may automatically populate the field with themost used value or the value used by another MFD with the same modelnumber. The user may then have the option to keep the value or enteranother value.

Although the method 500 describes a method where the values are receivedfrom the other networked MFDs in response to selection of a field, theMFD may also receive the values in advance and store the values in adatabase. The MFD may then use values in the database to present valuesin a pop-up window that can be selected by a user or to automaticallypopulate the fields for the settings in the configuration file. At block514, the method 500 ends.

FIG. 6 depicts a high-level block diagram of a computer that isdedicated to perform the functions described herein. As depicted in FIG.6 , the computer 600 comprises one or more hardware processor elements602 (e.g., a central processing unit (CPU), a microprocessor, or amulti-core processor), a memory 604, e.g., random access memory (RAM)and/or read only memory (ROM), a module 605 for automatically populatingparameters for configuration files via communication with networkedMFDs, and various input/output devices 606 (e.g., storage devices,including but not limited to, a tape drive, a floppy drive, a hard diskdrive or a compact disk drive, a receiver, a transmitter, a speaker, adisplay, a speech synthesizer, an output port, an input port and a userinput device (such as a keyboard, a keypad, a mouse, a microphone andthe like)). Although only one processor element is shown, it should benoted that the computer may employ a plurality of processor elements.

It should be noted that the present disclosure can be implemented insoftware and/or in a combination of software and hardware, e.g., usingapplication specific integrated circuits (ASIC), a programmable logicarray (PLA), including a field-programmable gate array (FPGA), or astate machine deployed on a hardware device, a computer or any otherhardware equivalents, e.g., computer readable instructions pertaining tothe method(s) discussed above can be used to configure a hardwareprocessor to perform the steps, functions and/or operations of the abovedisclosed methods. In one embodiment, instructions and data for thepresent module or process 605 for automatically populating parametersfor configuration files via communication with networked MFDs (e.g., asoftware program comprising computer-executable instructions) can beloaded into memory 604 and executed by hardware processor element 602 toimplement the steps, functions or operations as discussed above.Furthermore, when a hardware processor executes instructions to perform“operations,” this could include the hardware processor performing theoperations directly and/or facilitating, directing, or cooperating withanother hardware device or component (e.g., a co-processor and the like)to perform the operations.

The processor executing the computer readable or software instructionsrelating to the above described method(s) can be perceived as aprogrammed processor or a specialized processor. As such, the presentmodule 605 for automatically populating parameters for configurationfiles via communication with networked MFDs (including associated datastructures) of the present disclosure can be stored on a tangible orphysical (broadly non-transitory) computer-readable storage device ormedium, e.g., volatile memory, non-volatile memory, ROM memory, RAMmemory, magnetic or optical drive, device or diskette and the like. Morespecifically, the computer-readable storage device may comprise anyphysical devices that provide the ability to store information such asdata and/or instructions to be accessed by a processor or a computingdevice such as a computer or an application server.

It will be appreciated that variants of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be combined intomany other different systems or applications. Various presentlyunforeseen or unanticipated alternatives, modifications, variations, orimprovements therein may be subsequently made by those skilled in theart which are also intended to be encompassed by the following claims.

What is claimed is:
 1. A multi-function device (MFD), comprising: acommunication interface to establish a communication path with anetwork; a user interface to display a plurality of fields associatedwith different settings of a configuration file of the MFD; a processor;and a non-transitory computer-readable medium storing a plurality ofinstructions, which when executed by the processor, causes the processorto perform operations, comprising: detect selection of a fieldassociated with a setting of the configuration file; establish aconnection with at least one networked MFD on the network; query the atleast one networked MFD for a value used in the field associated withthe setting of the configuration file that is selected; receive thevalue from the at least one networked MFD; and populate the field withthe value.
 2. The MFD of claim 1, wherein the at least one networked MFDcomprises a plurality of networked MFDs.
 3. The MFD of claim 2, whereineach MFD of the plurality of networked MFDs provides the value used inthe field associated with the settings in the configuration file that isselected.
 4. The MFD of claim 3, wherein the processor is to presentvalues in a pop-up window on the user interface in an order of most usedvalue to least used value.
 5. The MFD of claim 4, wherein the processoris to populate the field with the most used value.
 6. The MFD of claim4, wherein the processor is to populate the field with a selected valueselected by a user in the pop-up window.
 7. The MFD of claim 3, whereinthe processor is to: query the plurality of networked MFDs for modelnumbers; identify a subset of MFDs from the plurality of networked MFDsthat have a same model number as the MFD based on the model numbers ofthe plurality of networked MFDs that are received; and present values ina pop-up window on the user interface from the subset of MFDs that havethe same model number as the MFD.
 8. The MFD of claim 1, wherein theprocessor is further to: generate a database with the value receivedfrom the at least one networked MFD; present the database to a user whenselection of the field is detected; and receive a selection of the valuefrom the database to populate the field with the value that is selected.9. The MFD of claim 1, further comprising: a timer with a pre-definedexpiration time period, wherein the processor is to populate the fieldwith the value when the pre-defined expiration time period expires afterselection of the field is detected.
 10. A method, comprising: detecting,via a processor of a multi-function device (MFD), a selection of a fieldassociated with a setting of a configuration file; establishing, via theprocessor, a connection with at least one networked MFD on a network;querying, via the processor, the at least one networked MFD for a valueused in the field associated with the setting of the configuration filethat is selected; receiving, via the processor, the value from the atleast one networked MFD; and populating, via the processor, the fieldwith the value.
 11. The method of claim 10, wherein the at least onenetworked MFD comprises a plurality of networked MFDs.
 12. The method ofclaim 11, wherein each MFD of the plurality of networked MFDs providesthe value used in the field associated with the settings in theconfiguration file that is selected.
 13. The method of claim 12, furthercomprising: ordering, via the processor, values received from theplurality of MFDs in an order of most used value to least used value;and presenting, via the processor, the values that are ordered in apop-window on a user interface of the MFD.
 14. The method of claim 13,further comprising: populating, via the processor, the field with themost used value.
 15. The method of claim 13, further comprising:populating, via the processor, the field with a selected value selectedby a user in the pop-up window.
 16. The method of claim 11, furthercomprising: querying, via the processor, the plurality of networked MFDsfor model numbers; identifying, via the processor, a subset of MFDs fromthe plurality of networked MFDs that have a same model number as the MFDbased on the model numbers of the plurality of networked MFDs that arereceived; and presenting, via the processor, values in a pop-up windowon the user interface from the subset of MFDs that have the same modelnumber as the MFD.
 17. The method of claim 10, further comprising:generating, via the processor, a database with the value received fromthe at least one networked MFD; presenting, via the processor, thedatabase to a user when selection of the field is detected; andreceiving, via the processor, a selection of the value from the databaseto populate the field with the value that is selected.
 18. The method ofclaim 10, wherein the processor populates the field with the value whenexpiration of a timer is detected, wherein the timer starts whenselection of the field is detected.
 19. A multi-function device (MFD),comprising: a communication interface to establish a communication pathwith a network; a user interface to display a plurality of fieldsassociated with different settings of a configuration file of the MFD; aprocessor; and a non-transitory computer-readable medium storing aplurality of instructions, which when executed by the processor, causesthe processor to perform operations comprising: detect selection of afield associated with a setting of the configuration file; establish aconnection with a plurality of MFDs on the network; query the pluralityof MFDs for a value used in the field associated with the setting of theconfiguration file that is selected; receive values from the pluralityof networked MFDs; identify a most popular value that is used by one ormore of the plurality of networked MFDs with a model number that is sameas a model number of the MFD; populate the field with the most popularvalue; and receive confirmation to save the most popular value in thefield associated with the setting of the configuration file.
 20. The MFDof claim 19, further comprising: a timer with a pre-defined expirationtime period, wherein the processor is to populate the field with themost popular value when the pre-defined expiration time period expiresafter selection of the field is detected.